Generating the .prowcapc file
When you are ready to store your custom deployment configuration in a new .prowcapc file, you can do so by either of two methods:
In both cases, the Deployment Packager writes a log of the operation in the output directory where it creates the .prowcapc file. The log file has the extension .log and the same name as the .prowcapc file.
Interactive mode
Open the .wcd file and choose Deploy
Generate or click the 
button on the toolbar. The Deployment Packager validates the configuration as described in the preceding section.
If there are no errors, the Deployment Packager displays a prompt that lists the changes you have made—that is, differences between the original configuration and the one you have defined—as well as any warnings, and gives you the option of continuing or canceling the operation. After reviewing the information, click Yes to generate the new .prowcapc file, or click No to abort the operation.
When you click Yes, the Deployment Packager generates the new .prowcapc file in the specified output directory. The name of this file matches the value of the Application Name field.
Upon completion, a message identifies the new .prowcapc file (or indicates the errors that prevented successful generation of the file). It also identifies the log file for the operation.
Batch mode
If you have installed OpenEdge Studio, you can use the bprowcappdep.bat script to generate the .prowcapc file without running the Deployment Packager interactively. This file is installed in OpenEdge-Install-Directory\bin. (It is not available to users of the standalone Deployment Packager tool extracted from the prowcdp.zip file.)
You execute the script with a single argument, the path to the deployment configuration (.wcd) file. For example:
bprowcappdep c:\WebClient\deployment\MyApp.wcd
The validation and generation are performed as in interactive mode, with an important exception: Unless the validation process encounters errors (in which case the operation terminates), generation of the .prowcapc file proceeds with no option to cancel. Messages that precede the actual start of the generation process, including error notifications and warnings, are written to the console window; they do not appear in the log file. Therefore, when using the bprowcappdep.bat script, you should redirect the screen output to a file or take other steps to make sure you do not overlook important messages.